Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0747125bd16480a9b2177811fffbd678ecbda1cce882467d85a3c4134612051e

Tx prefix hash: bde3484def9c9b43575c35f6c308d2d4b7bab917c314c2b51fbc6ab2d053ba51
Tx public key: 5291d14c70864d3a6d9fbd6996c4482768abcddcab95b9a0aae0c25d444cd68c
Timestamp: 1708843670 Timestamp [UCT]: 2024-02-25 06:47:50 Age [y:d:h:m:s]: 01:114:10:30:45
Block: 965067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342728 RingCT/type: yes/0
Extra: 015291d14c70864d3a6d9fbd6996c4482768abcddcab95b9a0aae0c25d444cd68c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a049541fb43f66048237ce504a25bd5c642dd44a389b942126267eb61538041 0.600000000000 1424814 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": 965077, "vin": [ { "gen": { "height": 965067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a049541fb43f66048237ce504a25bd5c642dd44a389b942126267eb61538041" } } ], "extra": [ 1, 82, 145, 209, 76, 112, 134, 77, 58, 109, 159, 189, 105, 150, 196, 72, 39, 104, 171, 205, 220, 171, 149, 185, 160, 170, 224, 194, 93, 68, 76, 214, 140, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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