Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70d18b91ed56ed8b823508c6776f1f7f5310cf14371b012cf0edccee8bfd7a4

Tx prefix hash: 4e2521a0bb0da97633637b3b74f540b4cf21cf15b6e9cf4bf7b28c130c339042
Tx public key: e32226b4ac842fa1400a8ecef38b8618c4c2058c62cf8e0716da4de5ad56c7df
Timestamp: 1734491305 Timestamp [UCT]: 2024-12-18 03:08:25 Age [y:d:h:m:s]: 00:021:22:41:37
Block: 1177616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15667 RingCT/type: yes/0
Extra: 01e32226b4ac842fa1400a8ecef38b8618c4c2058c62cf8e0716da4de5ad56c7df0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e87e5042b47355ce2f80cb6fed5edb1b2877a4b3bc9ac45897eb7cfb085241 0.600000000000 1663989 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": 1177626, "vin": [ { "gen": { "height": 1177616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e87e5042b47355ce2f80cb6fed5edb1b2877a4b3bc9ac45897eb7cfb085241" } } ], "extra": [ 1, 227, 34, 38, 180, 172, 132, 47, 161, 64, 10, 142, 206, 243, 139, 134, 24, 196, 194, 5, 140, 98, 207, 142, 7, 22, 218, 77, 229, 173, 86, 199, 223, 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