Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6fe258c03e67e918345c6b6bfbf7b1aecf6e3099b35f4f5901f6058905e26f

Tx prefix hash: be7ba9784b01337a52c9c16614ead5847e8ca45ac2f6a534bdfa2e32a1772cce
Tx public key: 04489700ecb281de7a20fd3a4411aa417bd2e0b6ac2eba1909792242378ae7b2
Timestamp: 1713485762 Timestamp [UCT]: 2024-04-19 00:16:02 Age [y:d:h:m:s]: 00:341:04:48:02
Block: 1003540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243913 RingCT/type: yes/0
Extra: 0104489700ecb281de7a20fd3a4411aa417bd2e0b6ac2eba1909792242378ae7b202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad3e3b396cfc070a7517bb6e672e627ce30d021114ed2e7423ae5080ca49c5f3 0.600000000000 1464082 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": 1003550, "vin": [ { "gen": { "height": 1003540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad3e3b396cfc070a7517bb6e672e627ce30d021114ed2e7423ae5080ca49c5f3" } } ], "extra": [ 1, 4, 72, 151, 0, 236, 178, 129, 222, 122, 32, 253, 58, 68, 17, 170, 65, 123, 210, 224, 182, 172, 46, 186, 25, 9, 121, 34, 66, 55, 138, 231, 178, 2, 17, 0, 0, 0, 1, 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