Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb35dc237a268dc991262c6e9203d8502c2d53047d4245df1b64e80639fc81d

Tx prefix hash: 557cd6b16942a3807a8d6cfb5182c11e060693c438d08e5f3cf2808ab2e49265
Tx public key: d5686cc34ecda07924ee853dd2cff259808e25e6f4317744e01797c693c06988
Timestamp: 1705512449 Timestamp [UCT]: 2024-01-17 17:27:29 Age [y:d:h:m:s]: 01:041:20:21:18
Block: 937434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290973 RingCT/type: yes/0
Extra: 01d5686cc34ecda07924ee853dd2cff259808e25e6f4317744e01797c693c0698802110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5363912cdc84ea6f7afe70b6d2fae1efeb9955d9e6acd4d28946727a9a5149b1 0.600000000000 1395488 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": 937444, "vin": [ { "gen": { "height": 937434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5363912cdc84ea6f7afe70b6d2fae1efeb9955d9e6acd4d28946727a9a5149b1" } } ], "extra": [ 1, 213, 104, 108, 195, 78, 205, 160, 121, 36, 238, 133, 61, 210, 207, 242, 89, 128, 142, 37, 230, 244, 49, 119, 68, 224, 23, 151, 198, 147, 192, 105, 136, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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