Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d53b877cd18331d9f822af748f68636277c97cec8c7d8dcfc23140fbe1dd244

Tx prefix hash: b86d08f61f60b1678f3a0d76889115cf57d5cbbaef17b49c8fbd60241f14a50f
Tx public key: f609662add1af65d98f14f807c9f7c5bffe88fdce43d1357ffae03068222c6a0
Timestamp: 1705687968 Timestamp [UCT]: 2024-01-19 18:12:48 Age [y:d:h:m:s]: 01:150:08:13:47
Block: 938874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368482 RingCT/type: yes/0
Extra: 01f609662add1af65d98f14f807c9f7c5bffe88fdce43d1357ffae03068222c6a00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6603eb619a43ba4114c6fb48f283783cfed07eee21b7843ba5abbc63d75b2f78 0.600000000000 1396956 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": 938884, "vin": [ { "gen": { "height": 938874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6603eb619a43ba4114c6fb48f283783cfed07eee21b7843ba5abbc63d75b2f78" } } ], "extra": [ 1, 246, 9, 102, 42, 221, 26, 246, 93, 152, 241, 79, 128, 124, 159, 124, 91, 255, 232, 143, 220, 228, 61, 19, 87, 255, 174, 3, 6, 130, 34, 198, 160, 2, 17, 0, 0, 0, 3, 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