Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c801031c5dd6b37de81184a89e4330daa5db75fb14fdbe4d142988c6d1d9027e

Tx prefix hash: aeb5ccfed7e5d2e12ec76e3ea45e3789e66e7dfcb2f5564bff6f620f9410dbe4
Tx public key: 6c417687989080ab63abca5ac325785950ed9899a410ff75f9a98e7974d4d0ca
Timestamp: 1744844113 Timestamp [UCT]: 2025-04-16 22:55:13 Age [y:d:h:m:s]: 00:217:15:34:56
Block: 1263014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153274 RingCT/type: yes/0
Extra: 016c417687989080ab63abca5ac325785950ed9899a410ff75f9a98e7974d4d0ca0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69e9afb7eee8f740e6f0cfcf7fca0a0e1fbd176519428a177f113734d2a3d99a 0.600000000000 1750197 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": 1263024, "vin": [ { "gen": { "height": 1263014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69e9afb7eee8f740e6f0cfcf7fca0a0e1fbd176519428a177f113734d2a3d99a" } } ], "extra": [ 1, 108, 65, 118, 135, 152, 144, 128, 171, 99, 171, 202, 90, 195, 37, 120, 89, 80, 237, 152, 153, 164, 16, 255, 117, 249, 169, 142, 121, 116, 212, 208, 202, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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