Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d11d508d8b54f027251cb5ff747adfc0d75a6278efd245403b8ce7bc8fe7e357

Tx prefix hash: bb49a63c4fa5e0d7baeb653e8a5f33609814406751b08bdab7a98a809f9b794b
Tx public key: a4f27b676833a76809a7fc8c395211697b4180c8d5dfdf1cbce3c8bc9d22ff00
Timestamp: 1708770778 Timestamp [UCT]: 2024-02-24 10:32:58 Age [y:d:h:m:s]: 01:070:16:50:37
Block: 964469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311554 RingCT/type: yes/0
Extra: 01a4f27b676833a76809a7fc8c395211697b4180c8d5dfdf1cbce3c8bc9d22ff0002110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b59a51191d314ca51e75912becec027a2d9b3e87d4ac0bc0b98df6e39024eb 0.600000000000 1424210 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": 964479, "vin": [ { "gen": { "height": 964469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b59a51191d314ca51e75912becec027a2d9b3e87d4ac0bc0b98df6e39024eb" } } ], "extra": [ 1, 164, 242, 123, 103, 104, 51, 167, 104, 9, 167, 252, 140, 57, 82, 17, 105, 123, 65, 128, 200, 213, 223, 223, 28, 188, 227, 200, 188, 157, 34, 255, 0, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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