Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f705419cc5ed9a6197410f77e94fb7a83f504625144f412ca5242c185eb1e7d

Tx prefix hash: d15b474732b118bd0d2c35a303fe687ca1dc760d17d59c88e057240b26dea667
Tx public key: 238728d259fedd2873f2c94ae2db1e1a5aba2c3dcae32a14ee068a214062b5d2
Timestamp: 1713534026 Timestamp [UCT]: 2024-04-19 13:40:26 Age [y:d:h:m:s]: 01:198:19:36:22
Block: 1003947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400746 RingCT/type: yes/0
Extra: 01238728d259fedd2873f2c94ae2db1e1a5aba2c3dcae32a14ee068a214062b5d20211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bc33cb4e61ffe39643e2366c40c32473ed534de2348ceda9fa94a5caab978a3 0.600000000000 1464503 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": 1003957, "vin": [ { "gen": { "height": 1003947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bc33cb4e61ffe39643e2366c40c32473ed534de2348ceda9fa94a5caab978a3" } } ], "extra": [ 1, 35, 135, 40, 210, 89, 254, 221, 40, 115, 242, 201, 74, 226, 219, 30, 26, 90, 186, 44, 61, 202, 227, 42, 20, 238, 6, 138, 33, 64, 98, 181, 210, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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