Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166cd84f394fed9332fe93a51d88c498d477debb9d6693c3d4632f786edd95c6

Tx prefix hash: e6c96851ed9c2f5dfbf1a5141dd33965df3a2de4a57f89350f63f764a84a5a7e
Tx public key: 4522d5f8e7e646d8b9de3310f5e0c2f3c8f5a557e84771b36fc09c918210b572
Timestamp: 1661374548 Timestamp [UCT]: 2022-08-24 20:55:48 Age [y:d:h:m:s]: 02:244:17:10:45
Block: 573044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696159 RingCT/type: yes/0
Extra: 014522d5f8e7e646d8b9de3310f5e0c2f3c8f5a557e84771b36fc09c918210b572021100000002faf35c9c000000000000000000

1 output(s) for total of 7.749388691000 dcy

stealth address amount amount idx
00: 3f9f9eadf53d249c115610f5972f5b2b25a14e8f1a9e534307d65348514c2605 7.749388691000 1006320 of 0

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": 573054, "vin": [ { "gen": { "height": 573044 } } ], "vout": [ { "amount": 7749388691, "target": { "key": "3f9f9eadf53d249c115610f5972f5b2b25a14e8f1a9e534307d65348514c2605" } } ], "extra": [ 1, 69, 34, 213, 248, 231, 230, 70, 216, 185, 222, 51, 16, 245, 224, 194, 243, 200, 245, 165, 87, 232, 71, 113, 179, 111, 192, 156, 145, 130, 16, 181, 114, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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