Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5272d7d6cb162049367b1c96df8e7ec07d89a7a06f15f92cc4c76faf9ed4c1bb

Tx prefix hash: ab861e401ba1e951e2c7caf18804305658c844294088fb06bdbdbd3ce8efed7e
Tx public key: 426f3ccf7266a65a350da45d7f8cd6862236dcec06f80e67219815bb51da1ffd
Timestamp: 1759842686 Timestamp [UCT]: 2025-10-07 13:11:26 Age [y:d:h:m:s]: 00:039:08:54:53
Block: 1384763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28185 RingCT/type: yes/0
Extra: 01426f3ccf7266a65a350da45d7f8cd6862236dcec06f80e67219815bb51da1ffd021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2ef40c0c6413991536959012f471f88f9b978b1f8b5f7bf0d94a0a3bb0c6177 0.600000000000 1872920 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": 1384773, "vin": [ { "gen": { "height": 1384763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ef40c0c6413991536959012f471f88f9b978b1f8b5f7bf0d94a0a3bb0c6177" } } ], "extra": [ 1, 66, 111, 60, 207, 114, 102, 166, 90, 53, 13, 164, 93, 127, 140, 214, 134, 34, 54, 220, 236, 6, 248, 14, 103, 33, 152, 21, 187, 81, 218, 31, 253, 2, 17, 0, 0, 0, 1, 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