Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b7fba02ebfe31c75c2a2609cdf452a9fa17a12ba6cafa292d8e987ba7d0de6

Tx prefix hash: eb151ecdae7002dd92c1ddddb0249b7b1f9370c4931ca8f2359518eb25b889a4
Tx public key: 4ac8e8dd3b3b41ba1d77d43cd033d062833f67ec553e9e647c05b226ffc65a87
Timestamp: 1724501220 Timestamp [UCT]: 2024-08-24 12:07:00 Age [y:d:h:m:s]: 00:224:21:45:15
Block: 1094887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160595 RingCT/type: yes/0
Extra: 014ac8e8dd3b3b41ba1d77d43cd033d062833f67ec553e9e647c05b226ffc65a87021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ed0efda867676af60e2f678ad4e2373fbd74cbe36ec79eaa9d84189b19612d 0.600000000000 1570008 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": 1094897, "vin": [ { "gen": { "height": 1094887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ed0efda867676af60e2f678ad4e2373fbd74cbe36ec79eaa9d84189b19612d" } } ], "extra": [ 1, 74, 200, 232, 221, 59, 59, 65, 186, 29, 119, 212, 60, 208, 51, 208, 98, 131, 63, 103, 236, 85, 62, 158, 100, 124, 5, 178, 38, 255, 198, 90, 135, 2, 17, 0, 0, 0, 1, 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