Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c642beb488946650cac8c9bcca148f83a070800defd4fe96668cf46a2e5f05a

Tx prefix hash: 40e3e46f8c3475c9ad9a7c392fe45a898d0d3d1907a93be0c9a1a4feb7f84831
Tx public key: 981e7111d8fef7be7ef7bfe848a13fcda5c7276302ea07ace49ff099e131c3df
Timestamp: 1738645093 Timestamp [UCT]: 2025-02-04 04:58:13 Age [y:d:h:m:s]: 00:290:18:24:44
Block: 1211697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205576 RingCT/type: yes/0
Extra: 01981e7111d8fef7be7ef7bfe848a13fcda5c7276302ea07ace49ff099e131c3df021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3d8da5870217ef3f3b81d5d0b2bb35277545cd2306cb871710b593f960ccedd 0.600000000000 1698460 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": 1211707, "vin": [ { "gen": { "height": 1211697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3d8da5870217ef3f3b81d5d0b2bb35277545cd2306cb871710b593f960ccedd" } } ], "extra": [ 1, 152, 30, 113, 17, 216, 254, 247, 190, 126, 247, 191, 232, 72, 161, 63, 205, 165, 199, 39, 99, 2, 234, 7, 172, 228, 159, 240, 153, 225, 49, 195, 223, 2, 17, 0, 0, 0, 2, 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