Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 136bae29c4876a60ee457d60188dcd7e02ad040f80a021a41ce2e758ee334703

Tx prefix hash: d4fba290b1c25d1afe902f85b497f15aee7f8db1c01c8c1d685858383a8eb67b
Tx public key: 38055595925e5448b52240f6bb34ee8d17dee8a757fb118fb1b026ebda873d9e
Timestamp: 1732545222 Timestamp [UCT]: 2024-11-25 14:33:42 Age [y:d:h:m:s]: 00:135:07:54:30
Block: 1161464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96526 RingCT/type: yes/0
Extra: 0138055595925e5448b52240f6bb34ee8d17dee8a757fb118fb1b026ebda873d9e0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab4fc49fee6a0a870e1c1cbcd74415baad2e26a09ce45a0599d17d2cb4927ff2 0.600000000000 1647119 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": 1161474, "vin": [ { "gen": { "height": 1161464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab4fc49fee6a0a870e1c1cbcd74415baad2e26a09ce45a0599d17d2cb4927ff2" } } ], "extra": [ 1, 56, 5, 85, 149, 146, 94, 84, 72, 181, 34, 64, 246, 187, 52, 238, 141, 23, 222, 232, 167, 87, 251, 17, 143, 177, 176, 38, 235, 218, 135, 61, 158, 2, 17, 0, 0, 0, 7, 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