Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db22e04dd87f216c4421e17ef27b2f9adcd17f02d70b33e3ae58c0edb65ab04d

Tx prefix hash: 9a54ad74702125dec3b9498f5457c36f440c21d25506b43d5360d6c8ccf1f038
Tx public key: a3c859f55824f78633e4b5f4e2e81009b019f4ca5410120693f5232f0aaee3fd
Timestamp: 1715539342 Timestamp [UCT]: 2024-05-12 18:42:22 Age [y:d:h:m:s]: 00:308:08:06:19
Block: 1020600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220374 RingCT/type: yes/0
Extra: 01a3c859f55824f78633e4b5f4e2e81009b019f4ca5410120693f5232f0aaee3fd02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa75c229b30d14186478ba35547f23dc428221c4a1a5482cd69349fb3ae458f 0.600000000000 1484681 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": 1020610, "vin": [ { "gen": { "height": 1020600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa75c229b30d14186478ba35547f23dc428221c4a1a5482cd69349fb3ae458f" } } ], "extra": [ 1, 163, 200, 89, 245, 88, 36, 247, 134, 51, 228, 181, 244, 226, 232, 16, 9, 176, 25, 244, 202, 84, 16, 18, 6, 147, 245, 35, 47, 10, 174, 227, 253, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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