Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7f376c2dc984214220727fc1d8ddc3304e0151fe5006be3d246dbbced365a0

Tx prefix hash: 1649377e6c40b5f504b1714b6dd75fa35edf49780bc2a2c1084cdb3dd9b88e7f
Tx public key: 43dc288e3d94af78af6805de1d5ba1b56b79f7630a98286ec2d4a5f00668c91b
Timestamp: 1760890122 Timestamp [UCT]: 2025-10-19 16:08:42 Age [y:d:h:m:s]: 00:025:07:49:33
Block: 1393461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18116 RingCT/type: yes/0
Extra: 0143dc288e3d94af78af6805de1d5ba1b56b79f7630a98286ec2d4a5f00668c91b021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 224c8531ead51f65407da5e7f84f287843b03ab798303efdfc2a3940332fd897 0.600000000000 1881726 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": 1393471, "vin": [ { "gen": { "height": 1393461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "224c8531ead51f65407da5e7f84f287843b03ab798303efdfc2a3940332fd897" } } ], "extra": [ 1, 67, 220, 40, 142, 61, 148, 175, 120, 175, 104, 5, 222, 29, 91, 161, 181, 107, 121, 247, 99, 10, 152, 40, 110, 194, 212, 165, 240, 6, 104, 201, 27, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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