Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d618dd7878441bc30b21c80e25d0bfeeb3ca83a4b3f2e0757ac976b3fa3098

Tx prefix hash: 343583a51310f0c2a83df1d22a158302a80c255e32a6ba6b58c2e0395cd8da7d
Tx public key: e16623122b463cb0acdef3c4c0d0b9ae0dee90f66ecde8d3cac8310a633c6bbd
Timestamp: 1577640604 Timestamp [UCT]: 2019-12-29 17:30:04 Age [y:d:h:m:s]: 04:333:14:02:04
Block: 34451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127520 RingCT/type: yes/0
Extra: 01e16623122b463cb0acdef3c4c0d0b9ae0dee90f66ecde8d3cac8310a633c6bbd02110000002b8a2ee0d9000000000000000000

1 output(s) for total of 471.900449990000 dcy

stealth address amount amount idx
00: 220210712a43c97c4c4e3310069b2c54191967fd668f090d6fc25229e2dd4b11 471.900449990000 57983 of 0

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": 34461, "vin": [ { "gen": { "height": 34451 } } ], "vout": [ { "amount": 471900449990, "target": { "key": "220210712a43c97c4c4e3310069b2c54191967fd668f090d6fc25229e2dd4b11" } } ], "extra": [ 1, 225, 102, 35, 18, 43, 70, 60, 176, 172, 222, 243, 196, 192, 208, 185, 174, 13, 238, 144, 246, 110, 205, 232, 211, 202, 200, 49, 10, 99, 60, 107, 189, 2, 17, 0, 0, 0, 43, 138, 46, 224, 217, 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