Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a81f44e7904b527faa29b62b9bac5ee82c1978855346eaeb7674ce980e3c0bb

Tx prefix hash: d0a3ad2ff8c1527b293f01ff2e9d355092cf6287a756a6fabf0780ebce689072
Tx public key: aa6a9adbd9e5b6e0df7eea5558c737a69d12229936fd4362430ac53f9fa97b1e
Timestamp: 1749579404 Timestamp [UCT]: 2025-06-10 18:16:44 Age [y:d:h:m:s]: 00:161:04:57:53
Block: 1302225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112900 RingCT/type: yes/0
Extra: 01aa6a9adbd9e5b6e0df7eea5558c737a69d12229936fd4362430ac53f9fa97b1e021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62c7dd55ae7437cd90ba6679df640ea2d12380c59ab8d57670941d15e1a9645f 0.600000000000 1789794 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": 1302235, "vin": [ { "gen": { "height": 1302225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62c7dd55ae7437cd90ba6679df640ea2d12380c59ab8d57670941d15e1a9645f" } } ], "extra": [ 1, 170, 106, 154, 219, 217, 229, 182, 224, 223, 126, 234, 85, 88, 199, 55, 166, 157, 18, 34, 153, 54, 253, 67, 98, 67, 10, 197, 63, 159, 169, 123, 30, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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