Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1970f3682e0103636916bc7e1c6ee5106c9497f02cef488a2b8793878aab9b

Tx prefix hash: a540ecf02bf7ad53fb12bb6adf87e21d20b4797e915c3ec8f7c96052746c338e
Tx public key: b860b0bdf03c1b6519ff5fc408b9e5f801ae509d08b3d8a955316e17707b61c3
Timestamp: 1721877164 Timestamp [UCT]: 2024-07-25 03:12:44 Age [y:d:h:m:s]: 00:313:04:28:56
Block: 1073115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223797 RingCT/type: yes/0
Extra: 01b860b0bdf03c1b6519ff5fc408b9e5f801ae509d08b3d8a955316e17707b61c302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b97320b193086b440d4a05f675fa477342bd609b35042294c61e51377c346eb 0.600000000000 1545614 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": 1073125, "vin": [ { "gen": { "height": 1073115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b97320b193086b440d4a05f675fa477342bd609b35042294c61e51377c346eb" } } ], "extra": [ 1, 184, 96, 176, 189, 240, 60, 27, 101, 25, 255, 95, 196, 8, 185, 229, 248, 1, 174, 80, 157, 8, 179, 216, 169, 85, 49, 110, 23, 112, 123, 97, 195, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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