Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d080e5575ab413342d3954b06e303319ff8c0e7197eb38aa4cc600d857955c62

Tx prefix hash: 78bbae735265ab098c3a2b7eaf3271bd2f57596815a8b5a54e38ce23c40bf7e3
Tx public key: 1dd5033b415e897eead346bbcec7d3ca94cfcf3eb9f57ecdaa5d227be896c59d
Timestamp: 1583752757 Timestamp [UCT]: 2020-03-09 11:19:17 Age [y:d:h:m:s]: 04:295:23:13:58
Block: 79362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106293 RingCT/type: yes/0
Extra: 011dd5033b415e897eead346bbcec7d3ca94cfcf3eb9f57ecdaa5d227be896c59d021100000002c48ea382000000000000000000

1 output(s) for total of 334.997480043000 dcy

stealth address amount amount idx
00: c17d0abfceee25824f8bd72aa2a5d3533c7b0a1c3fdfd1d75020a61ae038e479 334.997480043000 145174 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": 79372, "vin": [ { "gen": { "height": 79362 } } ], "vout": [ { "amount": 334997480043, "target": { "key": "c17d0abfceee25824f8bd72aa2a5d3533c7b0a1c3fdfd1d75020a61ae038e479" } } ], "extra": [ 1, 29, 213, 3, 59, 65, 94, 137, 126, 234, 211, 70, 187, 206, 199, 211, 202, 148, 207, 207, 62, 185, 245, 126, 205, 170, 93, 34, 123, 232, 150, 197, 157, 2, 17, 0, 0, 0, 2, 196, 142, 163, 130, 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