Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c935418384050e43f0523b01a274432eef89ee8ec5ce1c0a5f0465c674bc489f

Tx prefix hash: 99efcd45af7988b5b4b676f0ea4dc452d06d20bee3056b891508296db8b30bfa
Tx public key: c779539f42484b1adaf1e5e565fe8aa6b4e0619ce94bea48b6330b29b6a2f750
Timestamp: 1577714563 Timestamp [UCT]: 2019-12-30 14:02:43 Age [y:d:h:m:s]: 05:102:10:57:42
Block: 35073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222995 RingCT/type: yes/0
Extra: 01c779539f42484b1adaf1e5e565fe8aa6b4e0619ce94bea48b6330b29b6a2f7500211000000074943cd9f000000000000000000

1 output(s) for total of 469.666350849000 dcy

stealth address amount amount idx
00: 7cb69b503b16b59807b6a3f0eb96af1e3373cf184118be58e50b7373002f999e 469.666350849000 59076 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": 35083, "vin": [ { "gen": { "height": 35073 } } ], "vout": [ { "amount": 469666350849, "target": { "key": "7cb69b503b16b59807b6a3f0eb96af1e3373cf184118be58e50b7373002f999e" } } ], "extra": [ 1, 199, 121, 83, 159, 66, 72, 75, 26, 218, 241, 229, 229, 101, 254, 138, 166, 180, 224, 97, 156, 233, 75, 234, 72, 182, 51, 11, 41, 182, 162, 247, 80, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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