Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620ec69254158986b53bb75c550b1daba7ebc6bad12baedd3fddc8a0e06bbad6

Tx prefix hash: 9eaa71d0347953196ae522988860371a33cdf943ffc3ab76135998eff782f2e9
Tx public key: a1ccbf13441611b31699b4ed4c773950c3ea0837f005c61d316d3498a3a23b52
Timestamp: 1726271371 Timestamp [UCT]: 2024-09-13 23:49:31 Age [y:d:h:m:s]: 00:136:23:43:52
Block: 1109541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97711 RingCT/type: yes/0
Extra: 01a1ccbf13441611b31699b4ed4c773950c3ea0837f005c61d316d3498a3a23b52021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae52d0b765a4f0ac66d645199cb38ffa7c8b8ad2e6b3a7a98ee96250d56876ea 0.600000000000 1587832 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": 1109551, "vin": [ { "gen": { "height": 1109541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae52d0b765a4f0ac66d645199cb38ffa7c8b8ad2e6b3a7a98ee96250d56876ea" } } ], "extra": [ 1, 161, 204, 191, 19, 68, 22, 17, 179, 22, 153, 180, 237, 76, 119, 57, 80, 195, 234, 8, 55, 240, 5, 198, 29, 49, 109, 52, 152, 163, 162, 59, 82, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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