Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39b3c1735b82396e79a601a518ed5fcba8703c35d0107c0092bd108f62e0ef64

Tx prefix hash: 3500e45313531a618aac20ac194f9a1c43b80f7f13b4f04aa02b7da50cd40a04
Tx public key: a262a382cb1f2a06f8cb601c63cb53ca3b6f34f28a0621882462eeba9964ec7e
Timestamp: 1712480072 Timestamp [UCT]: 2024-04-07 08:54:32 Age [y:d:h:m:s]: 01:025:09:34:48
Block: 995188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279143 RingCT/type: yes/0
Extra: 01a262a382cb1f2a06f8cb601c63cb53ca3b6f34f28a0621882462eeba9964ec7e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abeb4265be77b69ee4fae0d9da5a1d1f3f1570b1186412988272993004796938 0.600000000000 1455594 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": 995198, "vin": [ { "gen": { "height": 995188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abeb4265be77b69ee4fae0d9da5a1d1f3f1570b1186412988272993004796938" } } ], "extra": [ 1, 162, 98, 163, 130, 203, 31, 42, 6, 248, 203, 96, 28, 99, 203, 83, 202, 59, 111, 52, 242, 138, 6, 33, 136, 36, 98, 238, 186, 153, 100, 236, 126, 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