Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3050434f42410e84b267aeb49fc4398f73ab96a2001ef77514071bb211b55e83

Tx prefix hash: cc6336a5e845f3c1b3c87936ef6565ce707493e3c6e30a73b396d105ede8ab9f
Tx public key: 4ed22c7ab299d51a882bf7829326c4158a36038da837680c0d8555a9b4c48493
Timestamp: 1724450257 Timestamp [UCT]: 2024-08-23 21:57:37 Age [y:d:h:m:s]: 00:230:06:59:40
Block: 1094465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164447 RingCT/type: yes/0
Extra: 014ed22c7ab299d51a882bf7829326c4158a36038da837680c0d8555a9b4c48493021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6c66e903a32bf63b13f4c9c8d058fd88c4cb03bf0f5d44e8906119c5a711c19 0.600000000000 1569582 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": 1094475, "vin": [ { "gen": { "height": 1094465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6c66e903a32bf63b13f4c9c8d058fd88c4cb03bf0f5d44e8906119c5a711c19" } } ], "extra": [ 1, 78, 210, 44, 122, 178, 153, 213, 26, 136, 43, 247, 130, 147, 38, 196, 21, 138, 54, 3, 141, 168, 55, 104, 12, 13, 133, 85, 169, 180, 196, 132, 147, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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