Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3944234cb0126ef1d65463ed805a3744adc8b324ed4f39c0b3f0d2d0602959ca

Tx prefix hash: 70d3821085ecf7bdf9f21a7e91e7959768625a9657cc6394b17dca9da55ca414
Tx public key: a9b6f810024a6a7ad2b3b0e724492adc8f0c2362e2fc15d219002aefe1137055
Timestamp: 1745351719 Timestamp [UCT]: 2025-04-22 19:55:19 Age [y:d:h:m:s]: 00:212:21:23:28
Block: 1267221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149869 RingCT/type: yes/0
Extra: 01a9b6f810024a6a7ad2b3b0e724492adc8f0c2362e2fc15d219002aefe11370550211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa28cb156fc691fbd360aa7836a30577432704241034cf15fd6f848ad8da91ba 0.600000000000 1754448 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": 1267231, "vin": [ { "gen": { "height": 1267221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa28cb156fc691fbd360aa7836a30577432704241034cf15fd6f848ad8da91ba" } } ], "extra": [ 1, 169, 182, 248, 16, 2, 74, 106, 122, 210, 179, 176, 231, 36, 73, 42, 220, 143, 12, 35, 98, 226, 252, 21, 210, 25, 0, 42, 239, 225, 19, 112, 85, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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