Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2adb1a02a42897726b030076c9a5642f913787cd3c95c6ec0378f0b1bd55626a

Tx prefix hash: 2eebbe9ebd681e6ac7c3a5bea144dda9f94519e7faeee7d3feb91cd24f987882
Tx public key: e26d3f69311264fd808de51ca7f28b4dfc698883678b4dfa307e098d99ec4947
Timestamp: 1728306488 Timestamp [UCT]: 2024-10-07 13:08:08 Age [y:d:h:m:s]: 01:032:17:44:01
Block: 1126427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281770 RingCT/type: yes/0
Extra: 01e26d3f69311264fd808de51ca7f28b4dfc698883678b4dfa307e098d99ec494702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 651ff7f75af3ea899159a02df3044072edec01dcc857b6556f6fece865a1b32f 0.600000000000 1609218 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": 1126437, "vin": [ { "gen": { "height": 1126427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "651ff7f75af3ea899159a02df3044072edec01dcc857b6556f6fece865a1b32f" } } ], "extra": [ 1, 226, 109, 63, 105, 49, 18, 100, 253, 128, 141, 229, 28, 167, 242, 139, 77, 252, 105, 136, 131, 103, 139, 77, 250, 48, 126, 9, 141, 153, 236, 73, 71, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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