Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab7c1b4727ad712ec69f0c1ad7578d7ad18405db99dfd5748bf39994e53dfd7

Tx prefix hash: fcdd24e860f08a1a19ac7ad21df02827520e93d08663c488f8f97744c7fa187b
Tx public key: d21fe8f08f4e84c1fc7233b72ada4db5f5ee797474e17221c7de0b9ebdc267cd
Timestamp: 1577794577 Timestamp [UCT]: 2019-12-31 12:16:17 Age [y:d:h:m:s]: 04:325:00:17:20
Block: 35718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121394 RingCT/type: yes/0
Extra: 01d21fe8f08f4e84c1fc7233b72ada4db5f5ee797474e17221c7de0b9ebdc267cd0211000000038a2ee0d9000000000000000000

1 output(s) for total of 467.368870364000 dcy

stealth address amount amount idx
00: 3c83e21acd0e5d3fae35527f28bbd946643aa91f0b3048e4a0d4f78c6078cc37 467.368870364000 60316 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": 35728, "vin": [ { "gen": { "height": 35718 } } ], "vout": [ { "amount": 467368870364, "target": { "key": "3c83e21acd0e5d3fae35527f28bbd946643aa91f0b3048e4a0d4f78c6078cc37" } } ], "extra": [ 1, 210, 31, 232, 240, 143, 78, 132, 193, 252, 114, 51, 183, 42, 218, 77, 181, 245, 238, 121, 116, 116, 225, 114, 33, 199, 222, 11, 158, 189, 194, 103, 205, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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