Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2bb50d77e29de238f84baac676a4cd1b5e243cf6482e18c1363a96eaf522e14

Tx prefix hash: d3d37032739904af0c19fa3bca722293e1d68d5cbf38f4a3a87402bf38421e9a
Tx public key: c204ae58b9333dc23a3deea689c113c26c49603a12eba97ef0822c45da05b95d
Timestamp: 1763139454 Timestamp [UCT]: 2025-11-14 16:57:34 Age [y:d:h:m:s]: 00:074:08:08:16
Block: 1412076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53044 RingCT/type: yes/0
Extra: 01c204ae58b9333dc23a3deea689c113c26c49603a12eba97ef0822c45da05b95d021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95603686f8b98a3e3770b9725a11f2fdc3e72d3aafc97aeafe5badb5b4c9e649 0.600000000000 1900541 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": 1412086, "vin": [ { "gen": { "height": 1412076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95603686f8b98a3e3770b9725a11f2fdc3e72d3aafc97aeafe5badb5b4c9e649" } } ], "extra": [ 1, 194, 4, 174, 88, 185, 51, 61, 194, 58, 61, 238, 166, 137, 193, 19, 194, 108, 73, 96, 58, 18, 235, 169, 126, 240, 130, 44, 69, 218, 5, 185, 93, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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