Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a561184915a315196c2eea07f50830efd756eeb6cd8a1b3b650e14e12e6a359

Tx prefix hash: 12fa0998f7ece1c3f11ced69c869ef4a622e045749f913d7c4d7d41289eedca7
Tx public key: 24dd50e3c2a7e835e6661af07b660d45fdf81e0eda3766c1eca9716fd85e2575
Timestamp: 1724742298 Timestamp [UCT]: 2024-08-27 07:04:58 Age [y:d:h:m:s]: 01:067:04:06:16
Block: 1096861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306458 RingCT/type: yes/0
Extra: 0124dd50e3c2a7e835e6661af07b660d45fdf81e0eda3766c1eca9716fd85e2575021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9a5b476ac3846faf0af43ea32e9f0122d294b68275236ae42d5f07d80c92361 0.600000000000 1572064 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": 1096871, "vin": [ { "gen": { "height": 1096861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9a5b476ac3846faf0af43ea32e9f0122d294b68275236ae42d5f07d80c92361" } } ], "extra": [ 1, 36, 221, 80, 227, 194, 167, 232, 53, 230, 102, 26, 240, 123, 102, 13, 69, 253, 248, 30, 14, 218, 55, 102, 193, 236, 169, 113, 111, 216, 94, 37, 117, 2, 17, 0, 0, 0, 8, 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