Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950bd35cba4b056c419654c9281220a524b25b3c14f3eac8180a54e9dd5e0a86

Tx prefix hash: b517810efce1532870e9b7969f8a22456c8d484872ea5de57fe904768ef888c5
Tx public key: 103975e0ab81b70f60b8a5d61ec38b26432ee859b772d31e6ea83402f79a0a4a
Timestamp: 1676178204 Timestamp [UCT]: 2023-02-12 05:03:24 Age [y:d:h:m:s]: 01:338:08:38:35
Block: 695138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502781 RingCT/type: yes/0
Extra: 01103975e0ab81b70f60b8a5d61ec38b26432ee859b772d31e6ea83402f79a0a4a0211000000015029cbac000000000000000000

1 output(s) for total of 3.052946269000 dcy

stealth address amount amount idx
00: f3d721c28aad757571b36e35b7b2237f718baf77b80ed98fc07bd7fb80ee9bd0 3.052946269000 1138081 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": 695148, "vin": [ { "gen": { "height": 695138 } } ], "vout": [ { "amount": 3052946269, "target": { "key": "f3d721c28aad757571b36e35b7b2237f718baf77b80ed98fc07bd7fb80ee9bd0" } } ], "extra": [ 1, 16, 57, 117, 224, 171, 129, 183, 15, 96, 184, 165, 214, 30, 195, 139, 38, 67, 46, 232, 89, 183, 114, 211, 30, 110, 168, 52, 2, 247, 154, 10, 74, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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