Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0bf64283f94ace39d2bdc0be5099e363f93ba854c4de5bfab4512a2921fd65

Tx prefix hash: 6735c5f337c19800fc99d62bb6b813ba5d1873c5c59700dc5ca6e0468cc8b882
Tx public key: 9a44bda15774a6aa5dac4681fe7bd637a208df6c68d1e1a6ce762d67c0df12d4
Timestamp: 1729422984 Timestamp [UCT]: 2024-10-20 11:16:24 Age [y:d:h:m:s]: 00:034:20:55:55
Block: 1135662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24896 RingCT/type: yes/0
Extra: 019a44bda15774a6aa5dac4681fe7bd637a208df6c68d1e1a6ce762d67c0df12d4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0523f4160a968b6bd3db8f1e002632f2a95044d60cea9403f3bca561fdd8148f 0.600000000000 1619001 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": 1135672, "vin": [ { "gen": { "height": 1135662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0523f4160a968b6bd3db8f1e002632f2a95044d60cea9403f3bca561fdd8148f" } } ], "extra": [ 1, 154, 68, 189, 161, 87, 116, 166, 170, 93, 172, 70, 129, 254, 123, 214, 55, 162, 8, 223, 108, 104, 209, 225, 166, 206, 118, 45, 103, 192, 223, 18, 212, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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