Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86759c45a82ca6235cd35f10d95d6f0fa3ae013b63387b145d73f5658aaac82

Tx prefix hash: 9f28688a3a0f16a18f6e96ec0f3b4b374a4b3cb714c43cbeef20c79384815aa8
Tx public key: 6cd7a3e122a8fc3e89e6f7b494eca3a57c6e0c085fad0dc3698915b5f96b4d59
Timestamp: 1705852482 Timestamp [UCT]: 2024-01-21 15:54:42 Age [y:d:h:m:s]: 01:129:12:11:22
Block: 940238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353704 RingCT/type: yes/0
Extra: 016cd7a3e122a8fc3e89e6f7b494eca3a57c6e0c085fad0dc3698915b5f96b4d5902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4427ce01350369a36eddc78874df8a72c4c106463aba8ecfa96fdddd2c91e54 0.600000000000 1398372 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": 940248, "vin": [ { "gen": { "height": 940238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4427ce01350369a36eddc78874df8a72c4c106463aba8ecfa96fdddd2c91e54" } } ], "extra": [ 1, 108, 215, 163, 225, 34, 168, 252, 62, 137, 230, 247, 180, 148, 236, 163, 165, 124, 110, 12, 8, 95, 173, 13, 195, 105, 137, 21, 181, 249, 107, 77, 89, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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