Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 736a8380269920b33e3f77d373a9febe5bdedc1df8ec0eb4dc11569b091c44cd

Tx prefix hash: fda291505114b118a7593712eb0422168f1d9dfb7dd295e1856b4f63f65a1ce7
Tx public key: 27dab44ebb2c75f7a49f5c920827966b3ef77b15cb7034a7d36fe1dfc8b95078
Timestamp: 1706260517 Timestamp [UCT]: 2024-01-26 09:15:17 Age [y:d:h:m:s]: 01:283:12:19:15
Block: 943616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461431 RingCT/type: yes/0
Extra: 0127dab44ebb2c75f7a49f5c920827966b3ef77b15cb7034a7d36fe1dfc8b950780211000000010c35fb00000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c78e84909dd7cbb764525a12bb23dcca45f8fa76a62644c210d0a062e0a082 0.600000000000 1401824 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": 943626, "vin": [ { "gen": { "height": 943616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c78e84909dd7cbb764525a12bb23dcca45f8fa76a62644c210d0a062e0a082" } } ], "extra": [ 1, 39, 218, 180, 78, 187, 44, 117, 247, 164, 159, 92, 146, 8, 39, 150, 107, 62, 247, 123, 21, 203, 112, 52, 167, 211, 111, 225, 223, 200, 185, 80, 120, 2, 17, 0, 0, 0, 1, 12, 53, 251, 0, 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