Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5829f20f45b5aba818cabfbea95e0318cc18b5d72e46fbc95931e11fa1a4ee21

Tx prefix hash: 0a3c68948473a518cd7d88fae425c4ceab557646f9977275cf9e324c3881fb52
Tx public key: 44d572ca6313a3bb51224d87e9a02c4ad3e885c42fe09d7b4e66c3dd3a22d0c0
Timestamp: 1726422048 Timestamp [UCT]: 2024-09-15 17:40:48 Age [y:d:h:m:s]: 00:206:00:31:40
Block: 1110792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147078 RingCT/type: yes/0
Extra: 0144d572ca6313a3bb51224d87e9a02c4ad3e885c42fe09d7b4e66c3dd3a22d0c0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b17a0316c18717191da85060467262a619e98f9fe8914fc2afdc38e0e60f693b 0.600000000000 1589527 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1110802, "vin": [ { "gen": { "height": 1110792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b17a0316c18717191da85060467262a619e98f9fe8914fc2afdc38e0e60f693b" } } ], "extra": [ 1, 68, 213, 114, 202, 99, 19, 163, 187, 81, 34, 77, 135, 233, 160, 44, 74, 211, 232, 133, 196, 47, 224, 157, 123, 78, 102, 195, 221, 58, 34, 208, 192, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8