Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89edcd05168dcaf68047d042dade34c351c35a994c097c18e40c8ae42c433d4

Tx prefix hash: 502ca71037ec9c7e804cec99c7550a0a8351f1b34aaf839b5a5f3dc8e87efa2e
Tx public key: ce55f7d29169c28529c8aae055f7fa3751b84fd6a20429412084dc5b7f498459
Timestamp: 1764051765 Timestamp [UCT]: 2025-11-25 06:22:45 Age [y:d:h:m:s]: 00:001:08:01:32
Block: 1419636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 955 RingCT/type: yes/0
Extra: 01ce55f7d29169c28529c8aae055f7fa3751b84fd6a20429412084dc5b7f4984590211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e4e0ce7b26a099a190695ee4276ece348fda827ab6f411a2841f47a3726e44e 0.600000000000 1908173 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": 1419646, "vin": [ { "gen": { "height": 1419636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e4e0ce7b26a099a190695ee4276ece348fda827ab6f411a2841f47a3726e44e" } } ], "extra": [ 1, 206, 85, 247, 210, 145, 105, 194, 133, 41, 200, 170, 224, 85, 247, 250, 55, 81, 184, 79, 214, 162, 4, 41, 65, 32, 132, 220, 91, 127, 73, 132, 89, 2, 17, 0, 0, 0, 2, 140, 235, 127, 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