Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62fc12a5a39a845f4bf6c03ca7c08c6368229e75faba28f762aa78c8c44b7e6

Tx prefix hash: 3e142e2f79386ccb9d57ad808349411fc1ec98758ef2dc89348b933f5bb4a105
Tx public key: bf8961306c4e1016ba0fbe63640ff01f650d91309c78d0d1428fcab9a9279b3c
Timestamp: 1737299177 Timestamp [UCT]: 2025-01-19 15:06:17 Age [y:d:h:m:s]: 00:151:17:40:43
Block: 1200784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108152 RingCT/type: yes/0
Extra: 01bf8961306c4e1016ba0fbe63640ff01f650d91309c78d0d1428fcab9a9279b3c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc44d06981145793bee7a048c7fd9e48d3736bfd532189d5be9ce6f85f4ced7c 0.600000000000 1687431 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": 1200794, "vin": [ { "gen": { "height": 1200784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc44d06981145793bee7a048c7fd9e48d3736bfd532189d5be9ce6f85f4ced7c" } } ], "extra": [ 1, 191, 137, 97, 48, 108, 78, 16, 22, 186, 15, 190, 99, 100, 15, 240, 31, 101, 13, 145, 48, 156, 120, 208, 209, 66, 143, 202, 185, 169, 39, 155, 60, 2, 17, 0, 0, 0, 1, 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