Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a2b23a97825470a05b1629fe3a7fe37e7903aaf1b8f67c6b308fa03789be36

Tx prefix hash: 634b8f925e338b2476ea317b044c9fdc8418ca33f08ee648181a1c074252911f
Tx public key: 86756a934e2f3720606b2e03b22faad76e90068916d86db150a6f0d6eac7075e
Timestamp: 1705391897 Timestamp [UCT]: 2024-01-16 07:58:17 Age [y:d:h:m:s]: 01:089:06:07:17
Block: 936420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324907 RingCT/type: yes/0
Extra: 0186756a934e2f3720606b2e03b22faad76e90068916d86db150a6f0d6eac7075e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4a898028be5cf221273b45cfe6d7eeef65602c7d1226fa636acd6df30a10f7 0.600000000000 1394446 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": 936430, "vin": [ { "gen": { "height": 936420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4a898028be5cf221273b45cfe6d7eeef65602c7d1226fa636acd6df30a10f7" } } ], "extra": [ 1, 134, 117, 106, 147, 78, 47, 55, 32, 96, 107, 46, 3, 178, 47, 170, 215, 110, 144, 6, 137, 22, 216, 109, 177, 80, 166, 240, 214, 234, 199, 7, 94, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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