Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483af78a5af3450a04f5c340d06c77adc80c0815f9a893bd24e2eb786d908205

Tx prefix hash: 40d19e8cc6665b238f0ee2771e657ef99ebcfa2c1ba71e8ae22c6aedf1ba5ad5
Tx public key: 6d46b35109b5e7a82c75fb99e8109cd412c012dd7943f8296fe1e49a0fef8bea
Timestamp: 1757169543 Timestamp [UCT]: 2025-09-06 14:39:03 Age [y:d:h:m:s]: 00:088:04:20:34
Block: 1362698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63059 RingCT/type: yes/0
Extra: 016d46b35109b5e7a82c75fb99e8109cd412c012dd7943f8296fe1e49a0fef8bea021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d96c363e4d6a2f73132725f3a646c47e1aff60144207456a4498ddf8d229f4ce 0.600000000000 1850729 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": 1362708, "vin": [ { "gen": { "height": 1362698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d96c363e4d6a2f73132725f3a646c47e1aff60144207456a4498ddf8d229f4ce" } } ], "extra": [ 1, 109, 70, 179, 81, 9, 181, 231, 168, 44, 117, 251, 153, 232, 16, 156, 212, 18, 192, 18, 221, 121, 67, 248, 41, 111, 225, 228, 154, 15, 239, 139, 234, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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