Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574f21eb84c2108952cfef8dcbe11b4e01454cf3d091618c735538c8f58cc779

Tx prefix hash: e4638b9c703e0bf5e3546b37ed5cb460fe9c5acd48488a3c4013ffce8da23901
Tx public key: 8467fed15ce643c5e089438e7861dcab0b15b36c352a82eb3a9d7b06f1f5455a
Timestamp: 1764805983 Timestamp [UCT]: 2025-12-03 23:53:03 Age [y:d:h:m:s]: 00:001:03:10:07
Block: 1425892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 818 RingCT/type: yes/0
Extra: 018467fed15ce643c5e089438e7861dcab0b15b36c352a82eb3a9d7b06f1f5455a021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86cdf69250e2468183870d54cc1fcef26e7fc9513d25cb57d873e0008a17cc5a 0.600000000000 1914575 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": 1425902, "vin": [ { "gen": { "height": 1425892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86cdf69250e2468183870d54cc1fcef26e7fc9513d25cb57d873e0008a17cc5a" } } ], "extra": [ 1, 132, 103, 254, 209, 92, 230, 67, 197, 224, 137, 67, 142, 120, 97, 220, 171, 11, 21, 179, 108, 53, 42, 130, 235, 58, 157, 123, 6, 241, 245, 69, 90, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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