Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfda30922692a9ca6a1d16b0611a890e8e11b2d8a57bc59ba5d9f943cbe79fb

Tx prefix hash: f3dad0697d606afb7dfe2e153c0cd5c7def53db943bb7dd6db5aa59be78e3f51
Tx public key: 743fec050c5f36de079b3e80a2b9ef5930ffb600991a1c0fe855f5bd6b7d5f16
Timestamp: 1705196130 Timestamp [UCT]: 2024-01-14 01:35:30 Age [y:d:h:m:s]: 01:102:17:02:54
Block: 934808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334525 RingCT/type: yes/0
Extra: 01743fec050c5f36de079b3e80a2b9ef5930ffb600991a1c0fe855f5bd6b7d5f160211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f7e2ecdef2e579529e49e7acc60b5ac66363996dd73ed1f0eb42b541b94960 0.600000000000 1392824 of 15

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": 934818, "vin": [ { "gen": { "height": 934808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f7e2ecdef2e579529e49e7acc60b5ac66363996dd73ed1f0eb42b541b94960" } } ], "extra": [ 1, 116, 63, 236, 5, 12, 95, 54, 222, 7, 155, 62, 128, 162, 185, 239, 89, 48, 255, 182, 0, 153, 26, 28, 15, 232, 85, 245, 189, 107, 125, 95, 22, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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