Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24a294f1f088111d5a9dd42f442648c1651db567108b4d9348d53a3af26dfff2

Tx prefix hash: ee67405e1ab1fe10e5a7bf7ee6dc82e28714a67156923019e26c55b0a9c33f65
Tx public key: c6f98deba9e41bd7bef73709c6cb7ee3fee531f1eeb30e18044b85db21a4ad25
Timestamp: 1736319818 Timestamp [UCT]: 2025-01-08 07:03:38 Age [y:d:h:m:s]: 00:069:12:06:35
Block: 1192714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49471 RingCT/type: yes/0
Extra: 01c6f98deba9e41bd7bef73709c6cb7ee3fee531f1eeb30e18044b85db21a4ad25021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb47a098364520b0e4d58d2af4ad92837f836e6fe2d9d7e9149f49dd3ac30823 0.600000000000 1679269 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": 1192724, "vin": [ { "gen": { "height": 1192714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb47a098364520b0e4d58d2af4ad92837f836e6fe2d9d7e9149f49dd3ac30823" } } ], "extra": [ 1, 198, 249, 141, 235, 169, 228, 27, 215, 190, 247, 55, 9, 198, 203, 126, 227, 254, 229, 49, 241, 238, 179, 14, 24, 4, 75, 133, 219, 33, 164, 173, 37, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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