Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 609f67e7b691c997cb7a977f272d2830089bc75f6574e4236cddd361469d4d6e

Tx prefix hash: c80d3647732ec9dbf068910a847a317813816d8ca569ed659e85f9efce54b824
Tx public key: 724fb34fedc2d1ad20058e49d3ac0a42ef2bce24ceb1d9c89a0c8de233d315f3
Timestamp: 1693479423 Timestamp [UCT]: 2023-08-31 10:57:03 Age [y:d:h:m:s]: 01:077:02:42:28
Block: 837863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316410 RingCT/type: yes/0
Extra: 01724fb34fedc2d1ad20058e49d3ac0a42ef2bce24ceb1d9c89a0c8de233d315f3021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.027571716000 dcy

stealth address amount amount idx
00: 4dba10dabeb183e5820265be10ef6da3d36739116cec349ba36bfc37c49c1e87 1.027571716000 1290537 of 0

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": 837873, "vin": [ { "gen": { "height": 837863 } } ], "vout": [ { "amount": 1027571716, "target": { "key": "4dba10dabeb183e5820265be10ef6da3d36739116cec349ba36bfc37c49c1e87" } } ], "extra": [ 1, 114, 79, 179, 79, 237, 194, 209, 173, 32, 5, 142, 73, 211, 172, 10, 66, 239, 43, 206, 36, 206, 177, 217, 200, 154, 12, 141, 226, 51, 211, 21, 243, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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