Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae2986dc1d5c47023b99088ef628fdb62b142bb215c0148f8e10b486684040f

Tx prefix hash: 8126cf258e4f2e815852b5d29207664c7e850d5f14d28aae7cc2c64532ca86ed
Tx public key: 99fb747669044b91445882a6df0ba7a72fdb6e08c6c6ae80fbbe2ed4cb071994
Timestamp: 1758972387 Timestamp [UCT]: 2025-09-27 11:26:27 Age [y:d:h:m:s]: 00:061:19:50:48
Block: 1377535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44277 RingCT/type: yes/0
Extra: 0199fb747669044b91445882a6df0ba7a72fdb6e08c6c6ae80fbbe2ed4cb071994021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327bc5bd85a7e13cc41aab390b92b86140480a7df295e8161ac5c1699b9e4eed 0.600000000000 1865630 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": 1377545, "vin": [ { "gen": { "height": 1377535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327bc5bd85a7e13cc41aab390b92b86140480a7df295e8161ac5c1699b9e4eed" } } ], "extra": [ 1, 153, 251, 116, 118, 105, 4, 75, 145, 68, 88, 130, 166, 223, 11, 167, 167, 47, 219, 110, 8, 198, 198, 174, 128, 251, 190, 46, 212, 203, 7, 25, 148, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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