Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3866f4c6976616e66d73b5edea776de129983d2c1a4e27d3a9f9908f25b6703

Tx prefix hash: a8a8265f81f9b35b7589d381f1bc3ced960d6a9447d5a64b7ea1de10b6ea405b
Tx public key: 4781820ba92e27c3221f1448fde4c7f32edb5044eaf98df9379a497e83c63c08
Timestamp: 1740832083 Timestamp [UCT]: 2025-03-01 12:28:03 Age [y:d:h:m:s]: 00:335:14:40:40
Block: 1229793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237539 RingCT/type: yes/0
Extra: 014781820ba92e27c3221f1448fde4c7f32edb5044eaf98df9379a497e83c63c08021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1cf0d7446763c7cf98bc343881c7b0d266e6109f86991f0385abf78699a5e68 0.600000000000 1716682 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": 1229803, "vin": [ { "gen": { "height": 1229793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1cf0d7446763c7cf98bc343881c7b0d266e6109f86991f0385abf78699a5e68" } } ], "extra": [ 1, 71, 129, 130, 11, 169, 46, 39, 195, 34, 31, 20, 72, 253, 228, 199, 243, 46, 219, 80, 68, 234, 249, 141, 249, 55, 154, 73, 126, 131, 198, 60, 8, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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