Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b6c052a49e4b484051c8a3caa8894fe45e761cf0970f47edf1855cb5e334bd0

Tx prefix hash: 98e26905376c5eee152e966419ea13fd073e9aaa783977dff570c32c16ce016c
Tx public key: 909ebc19be3ae3bea97aecca99c0f0e93d7807fbedab47f20df240433795df3d
Timestamp: 1737168557 Timestamp [UCT]: 2025-01-18 02:49:17 Age [y:d:h:m:s]: 00:058:09:39:05
Block: 1199738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41531 RingCT/type: yes/0
Extra: 01909ebc19be3ae3bea97aecca99c0f0e93d7807fbedab47f20df240433795df3d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a370de2822ea031c1d6f1950375645a2fb73b02ab524b342a29db3dfc2c12812 0.600000000000 1686371 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": 1199748, "vin": [ { "gen": { "height": 1199738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a370de2822ea031c1d6f1950375645a2fb73b02ab524b342a29db3dfc2c12812" } } ], "extra": [ 1, 144, 158, 188, 25, 190, 58, 227, 190, 169, 122, 236, 202, 153, 192, 240, 233, 61, 120, 7, 251, 237, 171, 71, 242, 13, 242, 64, 67, 55, 149, 223, 61, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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