Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6bdfb8d19c0de30953d94d301e026fdb31970e62b5366f7c4a7f283dd2d87d

Tx prefix hash: d2eee027febcf1708d9a7e4f183aa6e4d7cc56aa67fe32c11a33aa270927f16f
Tx public key: 1ead626e79788fdb7097ecd1b63a1e7a806682660933cb2bcc78d89626e9815e
Timestamp: 1737656874 Timestamp [UCT]: 2025-01-23 18:27:54 Age [y:d:h:m:s]: 00:145:08:57:32
Block: 1203745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103638 RingCT/type: yes/0
Extra: 011ead626e79788fdb7097ecd1b63a1e7a806682660933cb2bcc78d89626e9815e02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70f49a01a968da99e2a5ef80ce62ff5c5a16d33ec7889c2818c23b2573e993c 0.600000000000 1690424 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": 1203755, "vin": [ { "gen": { "height": 1203745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70f49a01a968da99e2a5ef80ce62ff5c5a16d33ec7889c2818c23b2573e993c" } } ], "extra": [ 1, 30, 173, 98, 110, 121, 120, 143, 219, 112, 151, 236, 209, 182, 58, 30, 122, 128, 102, 130, 102, 9, 51, 203, 43, 204, 120, 216, 150, 38, 233, 129, 94, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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