Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39c282e310c4fd05e0e8967b98708862edf4f7b3b64d067ef1614a7d38f29cd4

Tx prefix hash: 3f616bca8664748d6d0a4b10caf7df479b34c5cd196f9812b2fbc1e0fe6742f0
Tx public key: 970c0f24d1928fda5a058700115ab102e7c3b1dc4a566086a7009316ef6df831
Timestamp: 1577732314 Timestamp [UCT]: 2019-12-30 18:58:34 Age [y:d:h:m:s]: 05:003:08:46:10
Block: 35255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152356 RingCT/type: yes/0
Extra: 01970c0f24d1928fda5a058700115ab102e7c3b1dc4a566086a7009316ef6df831021100000017c5b5978f000000000000000000

1 output(s) for total of 469.014645811000 dcy

stealth address amount amount idx
00: df35e12fc9437818a0bcde49343e594739ac4215bb1684f7afd37b293e7f64ee 469.014645811000 59365 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": 35265, "vin": [ { "gen": { "height": 35255 } } ], "vout": [ { "amount": 469014645811, "target": { "key": "df35e12fc9437818a0bcde49343e594739ac4215bb1684f7afd37b293e7f64ee" } } ], "extra": [ 1, 151, 12, 15, 36, 209, 146, 143, 218, 90, 5, 135, 0, 17, 90, 177, 2, 231, 195, 177, 220, 74, 86, 96, 134, 167, 0, 147, 22, 239, 109, 248, 49, 2, 17, 0, 0, 0, 23, 197, 181, 151, 143, 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