Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3a5687e72f6768b578d09fe1fd388dd7652f222e20ae42e276ac72880dc4e5

Tx prefix hash: 7d6861f208be3bcc97804ba4680310f2d7cabdbc351a774273b844187df7b513
Tx public key: d9ac317ea5f985b1629f4f6edfae038d9f162fb955694c9f67c83fa070fd0634
Timestamp: 1730024368 Timestamp [UCT]: 2024-10-27 10:19:28 Age [y:d:h:m:s]: 00:027:18:31:04
Block: 1140627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19829 RingCT/type: yes/0
Extra: 01d9ac317ea5f985b1629f4f6edfae038d9f162fb955694c9f67c83fa070fd0634021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34f3d4dac13febce5b4223e5458465960645b8c63ef427b872849e9fe6c682bf 0.600000000000 1624428 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": 1140637, "vin": [ { "gen": { "height": 1140627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34f3d4dac13febce5b4223e5458465960645b8c63ef427b872849e9fe6c682bf" } } ], "extra": [ 1, 217, 172, 49, 126, 165, 249, 133, 177, 98, 159, 79, 110, 223, 174, 3, 141, 159, 22, 47, 185, 85, 105, 76, 159, 103, 200, 63, 160, 112, 253, 6, 52, 2, 17, 0, 0, 0, 1, 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