Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1dc481869005339b35a117d8d9294932e92bd952eb21de891a43de0eba6a28e

Tx prefix hash: 2e22244345a970602e71965778a03a0c13a1bdbdf81945d32f9308a59dfa58d2
Tx public key: c8f8840d6fa7e7e3149ab03eb39fe559564dca5560f7fb1a3af9b89ab8c60feb
Timestamp: 1575801700 Timestamp [UCT]: 2019-12-08 10:41:40 Age [y:d:h:m:s]: 05:087:14:29:36
Block: 23193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208412 RingCT/type: yes/0
Extra: 01c8f8840d6fa7e7e3149ab03eb39fe559564dca5560f7fb1a3af9b89ab8c60feb02110000000cad433a0b000000000000000000

1 output(s) for total of 514.251183850000 dcy

stealth address amount amount idx
00: cc168aabd46d2a90310cc589e79dc0e6a08d93c897b4a3ad8152a9795218bb29 514.251183850000 36882 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": 23203, "vin": [ { "gen": { "height": 23193 } } ], "vout": [ { "amount": 514251183850, "target": { "key": "cc168aabd46d2a90310cc589e79dc0e6a08d93c897b4a3ad8152a9795218bb29" } } ], "extra": [ 1, 200, 248, 132, 13, 111, 167, 231, 227, 20, 154, 176, 62, 179, 159, 229, 89, 86, 77, 202, 85, 96, 247, 251, 26, 58, 249, 184, 154, 184, 198, 15, 235, 2, 17, 0, 0, 0, 12, 173, 67, 58, 11, 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