Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a30bf4ab4c177a4aa493069cf298423653663a05a60003ad2c2a569cb41e6e

Tx prefix hash: c5911ec8a7722ab39c8bc25751353e2dfc0b944d00675819ce694fa0cc292f9c
Tx public key: ac59f827aa8a7d0630cd2c7578f12e75be78d6f68ffc623963020a87c4d29ac6
Timestamp: 1720296863 Timestamp [UCT]: 2024-07-06 20:14:23 Age [y:d:h:m:s]: 00:312:09:35:13
Block: 1060014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223244 RingCT/type: yes/0
Extra: 01ac59f827aa8a7d0630cd2c7578f12e75be78d6f68ffc623963020a87c4d29ac602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10a1cec9b41937e3123361e4e109e2bca86d2d13b12cf90bbcdf9ad6f974353a 0.600000000000 1530485 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": 1060024, "vin": [ { "gen": { "height": 1060014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10a1cec9b41937e3123361e4e109e2bca86d2d13b12cf90bbcdf9ad6f974353a" } } ], "extra": [ 1, 172, 89, 248, 39, 170, 138, 125, 6, 48, 205, 44, 117, 120, 241, 46, 117, 190, 120, 214, 246, 143, 252, 98, 57, 99, 2, 10, 135, 196, 210, 154, 198, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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