Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696e3b34c1e6a0c240142e4cf8d6787c441b1bca1296955a1bf92b915fb28278

Tx prefix hash: aa69a1e2a52117a09c2537d10fb02f4d8fa36cdd91b01adc3b2327b9bc8f83b8
Tx public key: 8c5bba30294c79a2faf1cd86f801a9721e870712bdff2f50c70137d45aced3f2
Timestamp: 1672966951 Timestamp [UCT]: 2023-01-06 01:02:31 Age [y:d:h:m:s]: 02:023:23:11:13
Block: 668495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538786 RingCT/type: yes/0
Extra: 018c5bba30294c79a2faf1cd86f801a9721e870712bdff2f50c70137d45aced3f2021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.741093125000 dcy

stealth address amount amount idx
00: e9b570a805e22f8f89cd0ab03e8a418395b66f1b276850a2a0fc28038ba09ea0 3.741093125000 1109746 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": 668505, "vin": [ { "gen": { "height": 668495 } } ], "vout": [ { "amount": 3741093125, "target": { "key": "e9b570a805e22f8f89cd0ab03e8a418395b66f1b276850a2a0fc28038ba09ea0" } } ], "extra": [ 1, 140, 91, 186, 48, 41, 76, 121, 162, 250, 241, 205, 134, 248, 1, 169, 114, 30, 135, 7, 18, 189, 255, 47, 80, 199, 1, 55, 212, 90, 206, 211, 242, 2, 17, 0, 0, 0, 1, 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