Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b856faee52443824d18656bc18a9c7de7ce0930a17f48e85fc623440a7c5a676

Tx prefix hash: a070c1fb9664bdcef7922da4115921e3ddbf033133f502cbf6b6f72be676f12b
Tx public key: 85e51b19a3711852fdfecebf4ef610668384f1c2c6bcb819ce2ad0af6c939568
Timestamp: 1699528783 Timestamp [UCT]: 2023-11-09 11:19:43 Age [y:d:h:m:s]: 01:083:18:35:29
Block: 887848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321028 RingCT/type: yes/0
Extra: 0185e51b19a3711852fdfecebf4ef610668384f1c2c6bcb819ce2ad0af6c939568021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.701763884000 dcy

stealth address amount amount idx
00: 8f2b4c46a5056522b968557427173dc4312e1614c45153a1906a6d19fd87d4b7 0.701763884000 1343753 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": 887858, "vin": [ { "gen": { "height": 887848 } } ], "vout": [ { "amount": 701763884, "target": { "key": "8f2b4c46a5056522b968557427173dc4312e1614c45153a1906a6d19fd87d4b7" } } ], "extra": [ 1, 133, 229, 27, 25, 163, 113, 24, 82, 253, 254, 206, 191, 78, 246, 16, 102, 131, 132, 241, 194, 198, 188, 184, 25, 206, 42, 208, 175, 108, 147, 149, 104, 2, 17, 0, 0, 0, 5, 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