Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5a9ccee8fd407c6ba3ed05ca6c3836b3b8392041927714454f21bbe75e94db

Tx prefix hash: 5f6da3955fca13058524a25feb87bbe9d31643d4cd6dcee8837cec7f1688f8de
Tx public key: e1758cf3c49c8ee13b5291dd6e127c77a4a308a70a8696af1618a773fffd9664
Timestamp: 1705432682 Timestamp [UCT]: 2024-01-16 19:18:02 Age [y:d:h:m:s]: 01:120:16:08:43
Block: 936766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347366 RingCT/type: yes/0
Extra: 01e1758cf3c49c8ee13b5291dd6e127c77a4a308a70a8696af1618a773fffd966402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 237969a847d8e62a698c0e72a30328b40c13ae128baf1f20846560ffa035cf4c 0.600000000000 1394806 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": 936776, "vin": [ { "gen": { "height": 936766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "237969a847d8e62a698c0e72a30328b40c13ae128baf1f20846560ffa035cf4c" } } ], "extra": [ 1, 225, 117, 140, 243, 196, 156, 142, 225, 59, 82, 145, 221, 110, 18, 124, 119, 164, 163, 8, 167, 10, 134, 150, 175, 22, 24, 167, 115, 255, 253, 150, 100, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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