Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99515d7f7f29a0b361ae3bd73be3e93b6d5356e93286c24025a3448a199ab904

Tx prefix hash: 4c7c3616b14c9fe5f47ba12998e6e79720380b856877541d4c76a43677598e6f
Tx public key: 15d5c4cb3773b97d8975802220d1208f525b2a9d1100a730ad47a8cd179599bf
Timestamp: 1735861539 Timestamp [UCT]: 2025-01-02 23:45:39 Age [y:d:h:m:s]: 00:165:16:38:53
Block: 1188926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118138 RingCT/type: yes/0
Extra: 0115d5c4cb3773b97d8975802220d1208f525b2a9d1100a730ad47a8cd179599bf021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec25163ccf091dfde1d47ad82ee14c399208a2814c671d5bf33a8da8751d8f5c 0.600000000000 1675431 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": 1188936, "vin": [ { "gen": { "height": 1188926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec25163ccf091dfde1d47ad82ee14c399208a2814c671d5bf33a8da8751d8f5c" } } ], "extra": [ 1, 21, 213, 196, 203, 55, 115, 185, 125, 137, 117, 128, 34, 32, 209, 32, 143, 82, 91, 42, 157, 17, 0, 167, 48, 173, 71, 168, 205, 23, 149, 153, 191, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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