Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78410ad7048daeefec8fbdc3c63ca1e639c916e6d2665f661d1ad1c9437ce4d5

Tx prefix hash: d1e276e161be4fec55800012be52a23721eeba37ca1ed38b599a2dbda0cc38d8
Tx public key: d2cb817ff1b83debf601b4601657c390d5cf29dead092a3da87f66f41febeea9
Timestamp: 1681962404 Timestamp [UCT]: 2023-04-20 03:46:44 Age [y:d:h:m:s]: 02:173:00:24:57
Block: 742450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643470 RingCT/type: yes/0
Extra: 01d2cb817ff1b83debf601b4601657c390d5cf29dead092a3da87f66f41febeea9021100000006faf35c9c000000000000000000

1 output(s) for total of 2.127919324000 dcy

stealth address amount amount idx
00: dd9a9488ebc732cdadd2906063d9c9c615c6c87b4ce00652827feb697991f8dc 2.127919324000 1189421 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": 742460, "vin": [ { "gen": { "height": 742450 } } ], "vout": [ { "amount": 2127919324, "target": { "key": "dd9a9488ebc732cdadd2906063d9c9c615c6c87b4ce00652827feb697991f8dc" } } ], "extra": [ 1, 210, 203, 129, 127, 241, 184, 61, 235, 246, 1, 180, 96, 22, 87, 195, 144, 213, 207, 41, 222, 173, 9, 42, 61, 168, 127, 102, 244, 31, 235, 238, 169, 2, 17, 0, 0, 0, 6, 250, 243, 92, 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