Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf3323a0f7d21fd17869a55dedd8ea3fbee17a4e44fc5dd5a5937a3a082c960

Tx prefix hash: 6c0f9673a3c5e2c6c2d2452db5041619acc3a72f54bc069e168809794ce45c1e
Tx public key: 539288af3acb6b9ed688dd847d1e6dd3af0f3cf819800bffb8374f91da016387
Timestamp: 1704381530 Timestamp [UCT]: 2024-01-04 15:18:50 Age [y:d:h:m:s]: 01:084:20:54:43
Block: 928076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321751 RingCT/type: yes/0
Extra: 01539288af3acb6b9ed688dd847d1e6dd3af0f3cf819800bffb8374f91da016387021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b42398f185b9dc82ca34217f43d96ee0917ac4214cc0d663b0b4a103f7765de 0.600000000000 1385932 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": 928086, "vin": [ { "gen": { "height": 928076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b42398f185b9dc82ca34217f43d96ee0917ac4214cc0d663b0b4a103f7765de" } } ], "extra": [ 1, 83, 146, 136, 175, 58, 203, 107, 158, 214, 136, 221, 132, 125, 30, 109, 211, 175, 15, 60, 248, 25, 128, 11, 255, 184, 55, 79, 145, 218, 1, 99, 135, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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