Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0dd878242bf2df141c41a2d3a54970b5b0b648e51593dd592b557578e26fb9

Tx prefix hash: fcf407aeb59d12b61f26324cd5ba8f7c4c97b49c0f803241a34f4761121f7df7
Tx public key: 1cfc3d2e2c5b5078400a8d3cf63473baf66c0a4185ef15232dc1340ab91b12ed
Timestamp: 1674013977 Timestamp [UCT]: 2023-01-18 03:52:57 Age [y:d:h:m:s]: 02:081:00:52:26
Block: 677173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579566 RingCT/type: yes/0
Extra: 011cfc3d2e2c5b5078400a8d3cf63473baf66c0a4185ef15232dc1340ab91b12ed0211000000018b7b6602000000000000000000

1 output(s) for total of 3.501423884000 dcy

stealth address amount amount idx
00: 364c320d0011260efc168426622c46340c4a21624e5cdb060fc7f4428d809e14 3.501423884000 1118940 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": 677183, "vin": [ { "gen": { "height": 677173 } } ], "vout": [ { "amount": 3501423884, "target": { "key": "364c320d0011260efc168426622c46340c4a21624e5cdb060fc7f4428d809e14" } } ], "extra": [ 1, 28, 252, 61, 46, 44, 91, 80, 120, 64, 10, 141, 60, 246, 52, 115, 186, 246, 108, 10, 65, 133, 239, 21, 35, 45, 193, 52, 10, 185, 27, 18, 237, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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