Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cde0d4acaafe350a1e20ba6aeba15f8172c40a1daaa531d8283adeb94c68103

Tx prefix hash: e3030bb85ae46fe16e9352b97a2f2d3aa04367804800efb8f24341cafda0493e
Tx public key: e6a99c24f14e3f7f8f5edd22f472212f801c17236be6d1121e3116039b3ff227
Timestamp: 1753119777 Timestamp [UCT]: 2025-07-21 17:42:57 Age [y:d:h:m:s]: 00:035:02:29:26
Block: 1330391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23964 RingCT/type: yes/0
Extra: 01e6a99c24f14e3f7f8f5edd22f472212f801c17236be6d1121e3116039b3ff22702110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bb55a8497e971d817920a64eda62b1a1853f1646fb5593ad4cdfd536e813abb 0.600000000000 1818182 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": 1330401, "vin": [ { "gen": { "height": 1330391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bb55a8497e971d817920a64eda62b1a1853f1646fb5593ad4cdfd536e813abb" } } ], "extra": [ 1, 230, 169, 156, 36, 241, 78, 63, 127, 143, 94, 221, 34, 244, 114, 33, 47, 128, 28, 23, 35, 107, 230, 209, 18, 30, 49, 22, 3, 155, 63, 242, 39, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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