Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714dac8e16858e2bb3ada6f5a495ab85d2feca92ba189694371a7d0caa848685

Tx prefix hash: 0c2a00d741fc13860f86f67e853f3f11d3f041bd3afeb024050c845adf4a6fb1
Tx public key: 9e67c0b8559081c4713d53aa934e859c38350414bac2bde5c65ce25fa083f48c
Timestamp: 1714317617 Timestamp [UCT]: 2024-04-28 15:20:17 Age [y:d:h:m:s]: 00:304:00:53:01
Block: 1010434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217332 RingCT/type: yes/0
Extra: 019e67c0b8559081c4713d53aa934e859c38350414bac2bde5c65ce25fa083f48c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9d5fe494f4d8fc9cc9f6dfeb8ea77c0e3934c35352f7c4af8bc844bd9c16735 0.600000000000 1472390 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": 1010444, "vin": [ { "gen": { "height": 1010434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9d5fe494f4d8fc9cc9f6dfeb8ea77c0e3934c35352f7c4af8bc844bd9c16735" } } ], "extra": [ 1, 158, 103, 192, 184, 85, 144, 129, 196, 113, 61, 83, 170, 147, 78, 133, 156, 56, 53, 4, 20, 186, 194, 189, 229, 198, 92, 226, 95, 160, 131, 244, 140, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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