Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e232fdf90ace95bb9b34bad2e025c2f49e4828a50ec868b559239135ba81d913

Tx prefix hash: 1dc0db9c8bf6c14cf48359edb6a86a8be82fe8d14ba7b8a423e4fa047b7b5eb7
Tx public key: 930aee6fa0e1716c2baa2cd93701e05a1b72cb53db3bb2421beed208573d9ebc
Timestamp: 1726989564 Timestamp [UCT]: 2024-09-22 07:19:24 Age [y:d:h:m:s]: 01:043:01:59:54
Block: 1115501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289192 RingCT/type: yes/0
Extra: 01930aee6fa0e1716c2baa2cd93701e05a1b72cb53db3bb2421beed208573d9ebc02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1b2549cc6ee4077ba9dc71d4c958bf127c398a752a509167b82bbfaca926c5f 0.600000000000 1595658 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": 1115511, "vin": [ { "gen": { "height": 1115501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1b2549cc6ee4077ba9dc71d4c958bf127c398a752a509167b82bbfaca926c5f" } } ], "extra": [ 1, 147, 10, 238, 111, 160, 225, 113, 108, 43, 170, 44, 217, 55, 1, 224, 90, 27, 114, 203, 83, 219, 59, 178, 66, 27, 238, 210, 8, 87, 61, 158, 188, 2, 17, 0, 0, 0, 12, 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