Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21bf1b6412084be4c7d5d530d7680015ff000014ba5a1fb2e856c91ec4ceec19

Tx prefix hash: 889a74e61fd69cd858c56d5989ff7de084c7ad8347b6778c6588a1e1c37ec255
Tx public key: 6054ff3e484c5e4b755ea39db5b849897f9ade953ab91958327a987e2d57fa70
Timestamp: 1762951413 Timestamp [UCT]: 2025-11-12 12:43:33 Age [y:d:h:m:s]: 00:041:05:45:57
Block: 1410522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29516 RingCT/type: yes/0
Extra: 016054ff3e484c5e4b755ea39db5b849897f9ade953ab91958327a987e2d57fa70021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64f6efeb2c0f1ebc73812daa6ffb3319b1d3c974215072dc3f161db5df4b261 0.600000000000 1898975 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": 1410532, "vin": [ { "gen": { "height": 1410522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64f6efeb2c0f1ebc73812daa6ffb3319b1d3c974215072dc3f161db5df4b261" } } ], "extra": [ 1, 96, 84, 255, 62, 72, 76, 94, 75, 117, 94, 163, 157, 181, 184, 73, 137, 127, 154, 222, 149, 58, 185, 25, 88, 50, 122, 152, 126, 45, 87, 250, 112, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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