Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca0c56bbd97a9f1dd4b4933d939c6380110ac355dd7b11355e52aa70f10ea4e

Tx prefix hash: 3fa47f4e6852bb3d6261f6cef2053bbd6ce6efda7b6e7299bc8afc808452f658
Tx public key: 77e171659c86848237974bd3923d9728f08a393742cbc63512ee40cb15ba929f
Timestamp: 1578937344 Timestamp [UCT]: 2020-01-13 17:42:24 Age [y:d:h:m:s]: 05:021:05:01:05
Block: 44845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165235 RingCT/type: yes/0
Extra: 0177e171659c86848237974bd3923d9728f08a393742cbc63512ee40cb15ba929f02110000008bdcee4b4d000000000000000000

1 output(s) for total of 435.923959376000 dcy

stealth address amount amount idx
00: c0de5486a5c89c0b0ee1fa3de4e14b6317b60a69138ce1d2a3b62595fb95a10f 435.923959376000 81728 of 0

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": 44855, "vin": [ { "gen": { "height": 44845 } } ], "vout": [ { "amount": 435923959376, "target": { "key": "c0de5486a5c89c0b0ee1fa3de4e14b6317b60a69138ce1d2a3b62595fb95a10f" } } ], "extra": [ 1, 119, 225, 113, 101, 156, 134, 132, 130, 55, 151, 75, 211, 146, 61, 151, 40, 240, 138, 57, 55, 66, 203, 198, 53, 18, 238, 64, 203, 21, 186, 146, 159, 2, 17, 0, 0, 0, 139, 220, 238, 75, 77, 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