Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97381f593d9802d06797087c910f4eeaf3702ee79cf3b976e578e00f23a909bb

Tx prefix hash: 06264741a963f8c9731a76799fa5c2fa0a144d08ad423a778d875cde46187599
Tx public key: 7cc10f59d7d08a694f021e028ae61fd1ed1bb0bdc9d5f95f6320554644a2332e
Timestamp: 1709188353 Timestamp [UCT]: 2024-02-29 06:32:33 Age [y:d:h:m:s]: 00:269:01:43:06
Block: 967929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192630 RingCT/type: yes/0
Extra: 017cc10f59d7d08a694f021e028ae61fd1ed1bb0bdc9d5f95f6320554644a2332e021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d2bb14fc4c165c3ff7da3c81b51564bccc2aae667221172d266045957e722f3 0.600000000000 1427722 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": 967939, "vin": [ { "gen": { "height": 967929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d2bb14fc4c165c3ff7da3c81b51564bccc2aae667221172d266045957e722f3" } } ], "extra": [ 1, 124, 193, 15, 89, 215, 208, 138, 105, 79, 2, 30, 2, 138, 230, 31, 209, 237, 27, 176, 189, 201, 213, 249, 95, 99, 32, 85, 70, 68, 162, 51, 46, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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