Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25713516189acd63741aa976902fc4c697867e88f071fcd3430ac17a6d97ea34

Tx prefix hash: 366afd32589b91982e764b6ef3eb39cf4171a0bd7ceb165d3da631742c85fade
Tx public key: 4c208b7f805d7c7f96d4a2501a63f53f4b158716716c403d3a3516bae8a1d9bd
Timestamp: 1761323059 Timestamp [UCT]: 2025-10-24 16:24:19 Age [y:d:h:m:s]: 00:012:09:25:44
Block: 1397043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8838 RingCT/type: yes/0
Extra: 014c208b7f805d7c7f96d4a2501a63f53f4b158716716c403d3a3516bae8a1d9bd021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8187f5a6e25b21925b4fc415f295dbffed718167c093123319ee2cde4b0ca7b4 0.600000000000 1885334 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": 1397053, "vin": [ { "gen": { "height": 1397043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8187f5a6e25b21925b4fc415f295dbffed718167c093123319ee2cde4b0ca7b4" } } ], "extra": [ 1, 76, 32, 139, 127, 128, 93, 124, 127, 150, 212, 162, 80, 26, 99, 245, 63, 75, 21, 135, 22, 113, 108, 64, 61, 58, 53, 22, 186, 232, 161, 217, 189, 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