Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1026a4f169812f2b43c6b17e4a37b05d97827c86212d20d1856f6f2314d23e3d

Tx prefix hash: 9bd9b5ee9e0836734b6af904522ab7de4e4e790152ec949b0692db6bfecfd60e
Tx public key: d97d75fd466516d67028e51ba0da874ed9e7a576580a8a298bf7bf8efd07ce25
Timestamp: 1722718536 Timestamp [UCT]: 2024-08-03 20:55:36 Age [y:d:h:m:s]: 00:249:06:14:16
Block: 1080091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178048 RingCT/type: yes/0
Extra: 01d97d75fd466516d67028e51ba0da874ed9e7a576580a8a298bf7bf8efd07ce2502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb85ed1d3436ab95ba2fc5ccf56949123159b9ec86d0aed240dd5d337dcef0e 0.600000000000 1553318 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": 1080101, "vin": [ { "gen": { "height": 1080091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb85ed1d3436ab95ba2fc5ccf56949123159b9ec86d0aed240dd5d337dcef0e" } } ], "extra": [ 1, 217, 125, 117, 253, 70, 101, 22, 214, 112, 40, 229, 27, 160, 218, 135, 78, 217, 231, 165, 118, 88, 10, 138, 41, 139, 247, 191, 142, 253, 7, 206, 37, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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