Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bac36eec6837b31df46d47cad304336381c9d74eba8df5b3b4f318a34bc1199

Tx prefix hash: 041d5c7b3a21c947cbe03dc03213e3094209bb5fa1d57dac056d98940b210666
Tx public key: 6a749d8233273e2d4ecefae6af53512cfaee333e7fcdf6a42346444f4f52c13d
Timestamp: 1732210580 Timestamp [UCT]: 2024-11-21 17:36:20 Age [y:d:h:m:s]: 00:211:04:50:01
Block: 1158690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150649 RingCT/type: yes/0
Extra: 016a749d8233273e2d4ecefae6af53512cfaee333e7fcdf6a42346444f4f52c13d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19b380f4cb2cc37f04941b100136fedfab19a7638b4d07bc50958c9dff9af31 0.600000000000 1644319 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": 1158700, "vin": [ { "gen": { "height": 1158690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19b380f4cb2cc37f04941b100136fedfab19a7638b4d07bc50958c9dff9af31" } } ], "extra": [ 1, 106, 116, 157, 130, 51, 39, 62, 45, 78, 206, 250, 230, 175, 83, 81, 44, 250, 238, 51, 62, 127, 205, 246, 164, 35, 70, 68, 79, 79, 82, 193, 61, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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